home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 26
/
Cream of the Crop 26.iso
/
bbs
/
qked_240.zip
/
QUIKEDIT.DOC
< prev
next >
Wrap
Text File
|
1997-07-27
|
81KB
|
1,633 lines
┌──────┐┌──┐┌──┐┌───┐┌──┐ ┌──┐┌─────┐┌───────┐┌───┐┌───────┐
│░▒┌┐░▒││░▒││░▒││░▒▓││░▒│┌┘░┌┘│░▒▓┌─┘│░▒▓┌┐░▒││░▒▓│└─┐░▒▓┌─┘
│▒▓││▒▓││▒▓││▒▓││▒▓█││▒▓└┘ └─┐│▒▓█└┐ │▒▓█││▒▓││▒▓█│ │▒▓█│
│▓█││▓█││▓█││▓█││▓██││▓█┌──┐▒││▓██┌┘ │▓██││▓█││▓██│ │▓██│
│██└┘██││██└┘██││███││██│ │▓││███└─┐│███└┘██││███│ │███│
└──────\└──────┘└───┘└──┘ └─┘└─────┘└───────┘└───┘ └───┘
Deluxe Fullscreen ANSI Message Editing Utility
For QuickBBS v2.7x / v2.8x, RemoteAccess v2.xx, Telegard v3.0x,
ProBoard v2.xx, AdeptXBBS v2.xx Watcom / v1.xx VAC, SynchroNet v2.xx,
TriBBS, Concord v0.01 & Compatibles
────────────────────────────────────────────────────────────────────────────
QuikEdit v2.40 - Copyright Matrix Technologies, 1994-97 - QuikEdit v2.40
────────────────────────────────────────────────────────────────────────────
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Some Unique Features Of QuikEdit v2.40 ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
■ QuikEdit has a built in Macro replacement feature that will replace
keywords with other words. Eg "QB" -> "QuickBBS"
■ QuikEdit has a built message censoring feature to weed out inappropriate
text. {+}
■ Character Color Configuration for individual letters such as Uppercase,
lowercase, High Bit, numbers, and punctuation.
■ Tagline appending feature - QuikEdit has THREE modes of tagline appending
available! Mode 1 is single random tagline appending without user
knowledge, Mode 2 is allow the user to select from a random pick list,
and Mode 3 allows the user to completely scan the entire tagline database
for the tagline they want! {+}
■ Easy to use control keys.
■ Color Code insert strings
■ SysOp defined function key macros
■ Quoted text re-formatting
And much MORE!
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Copyright Notices & Program Disclaimer ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
The utility QuikEdit, along with all its support files and documents, are
Copyright (C) 1994-97 Benjamin Schollnick. Distributing a version AFTER it
has been registered is prohibited; distribution & execution of the
original, unaltered version is permitted, indeed encouraged, as long as all
support-files and documentation that accompany the program are included
WITHOUT ALTERATION OF ANY SORT. None of the files included in the QuikEdit
archive may be modified in any way or distributed in any package without
the express, written permission of Matrix Technologies. Any type of cracking
of either evaluation or registered versions of QuikEdit including (but not
limited to) hex-editing, reverse engineering, decompiling are strictly
prohibited.
The author can be quickly reached for information through the QUICKBBS,
QUICKPRO, QUIKUTILS, ICEUTILS, PROBOARD or the RA_UTIL international
FidoNET Conferences, or at InterNET e-mail address:
QuickBBS@QuickBBS.Com or bscholl@eznet.net
Or, If you wish to trust comments/complaints/suggestions to the Post
Office, you can send them to:
Benjamin Schollnick
c/o Matrix Technologies
33 Valiant Drive
Rochester, New York 14623
The following programs mentioned in this documentation are Copyright of
their respective authors. They are listed in no particular order:
QuikEdit - Copyright Matrix Technologies & Benjamin Schollnick
QuickBBS - Copyright Matrix Technologies & Benjamin Schollnick
FKFossil - Copyright Tim Strike and Forbidden Knights Systems
RemoteAccess - Copyright Wantree Development & Andrew Milner
Telegard - Copyright Tim Strike
Concord - Copyright Pasi Talliniemi
ProBoard - Copyright Philippe Leybaert
Synchronet - Copyright Digital Dymantics
TriBBS - Copyright Freejack's Software & TriSoft
AdeptXBBS - Copyright AdeptSoft
X00 - Copyright Raymond L. Gwinn
BNU - Copyright David Nugent and Unique Computing Pty Limited
Turbo Pascal - Copyright Borland International
THE USUAL LEGALITIES
I (Benjamin Schollnick) make no warranty of any kind, expressed or implied,
including without limitation any warranties of merchantability and/or
fitness for a particular purpose. I shall not be held liable for any
damages, whether direct, indirect, special or consequential arising from
the failure of this program to operate in the manner desired by the user.
I shall not be held liable for any damage to data or property which may be
caused directly or indirectly by the use of this program.
In no event will I be held liable for any damages, including (but not
limited to) any lost profits, lost savings, or other incidental or
consequential damages arising out of the use -- or the inability to use --
this program, or for any claim by any other party.
The only thing that this package is guaranteed to do is to take up space
on your hard drive.
Making use of this software is acknowledgement that you have read,
understand, and fully agree to the license and disclaimer agreement.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Credits ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
We would like to thank all of the Beta sites, and users that have assisted
us in the development of QuikEdit.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Registration ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
This program is not Freeware. If this program satisfies your expectations
of a fullscreen editor,if not MORE, then you are expected to register it
after an evaluation period of 30 days or sooner. By doing this you can
be sure of continued development of the software. Thanks for your support.
This program may be freely distributed but DO NOT under any circumstances
change any of the executables or alter any files that come in the original
distribution archive.
I urge you to register as soon as you can! The more registrations that I
have will show the interest of people in the program, and I will release
future versions with many more features. If you register, the Message
Censoring & tagline features will become available. All "Unregistered"
messages and almost inaudible beeps within the program will also be removed.
Please note that the status of features (whether they are available or not
to unregistered users) may be changed without further warning in later
versions of the software; but this does not mean that they will be changed.
To register, fill out the REGISTER.DOC form and submit it to any of the
sites in REGSITE.LST. Thank you for your support.
Any Registration forms that have invalid or missing information may be
considered void and not be processed, depending on the extent of the
errors.
Due to recent events, I have changed my policy on personal cheques that are
sent in to pay for registration. I will continue to honor them, however as
of this release, there will be a 2 week hold placed on the cheque to ENSURE
that it does NOT go N.S.F. Although most people are honest about this,
lately too many people have sent in N.S.F. cheques, and when contacted
about them, show little or no concern about them or the financial
difficulties they may have caused.
Additionally, a service charge of $25 will be levied against any N.S.F.
cheques. Until both the full payment, and the service charge is received
in the form of a MONEY ORDER, the registration will not be processed.
In conclusion to the above information, to ensure a speedy turnaround time
it is recommended you send your registration in the form of a money order.
If you do choose to send in a personal cheque, it means that you have read,
understood and agree to these conditions.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Archive Contents ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
QuikEdit v2.40 has been compressed using PKZIP. This archive should have
an authenticity verification seal by Benjamin Schollnick. If this archive
is not in ZIP format, or if the seal has been broken, it is may be advisable
to get a new archive from one of the support sites listed at the end
of the documentation.
The QuikEdit archive should contain the following files :
QUIKEDIT.EXE - The main program
EDITCFG .EXE - Use to configure the program
CENSOR .CFG - Sample censor keyword file
QUIKEDIT.DOC - Program documentation
WHATSNEW.240 - Changes in QuikEdit since previous version
HISTORY .DOC - Changes in QuikEdit since it's creation
ADEPT .ZIP - QuikEdit / AdeptXBBS files
MAXIMUS .ZIP - Instructions for running QuikEdit with Maximus
FILE_ID .DIZ - General program description
REGISTER.DOC - QuikEdit Registration documentation
REGSITE .LST - QuikEdit registration Sites
UPGRADE .DOC - QuikEdit Upgrade Documentation
SWEDISH .LNG - QuikEdit Language File (Swedish)
FRENCH .LNG - QuikEdit Language File (French)
ENGLISH .LNG - QuikEdit Language File (English)
SPANISH .LNG - QuikEdit Language File (Spanish)
QUIKEDIT.LNG - QuikEdit Language File (English) [Default Language]
If one or any combination of these files are missing, or files have been
ADDED, then you are using a possibly modified or altered copy of QuikEdit.
It would be advised that you delete this copy, and get a clean copy of
QuikEdit from one of the BBS's listed at the end of the documentation.
Newest Version of QuikEdit can be F'REQed from Matrix Technologies BBS
under the magic name 'QUIKEDIT' (Without the quotes).
There is a second archive which you can probably find wherever you obtained
this copy of QuikEdit. The file is QUIKDICT.ZIP, which is an archive
containing QuikEdit's dictionary files. These files must be installed into
the program directory for QuikEdit to make use of the spell checker.
Files QuikEdit will create are :
QUIKEDIT.CFG - The configuration file.
QUIKEDIT.x - The temporary file which buffer text is stored in.
[x] represents current node number. This file also
indicates that the current node is in use.
MACRO.CFG - The file containing replacement macros.
MSGTMP. - Textfile containing message text which is read in
by the BBS package.
Files QuikEdit can/will read are:
CONFIG.RA - Read when QuikEdit is first installed. It will
CONFIG.TG attempt to determine if you are running QuickBBS,
QUICKCFG.DAT RemoteAccess or Telegard by use of a Environment
variable, and if it can find the configuration, it
will read in some information from it.
MESSAGES.RA - QuikEdit will attempt to read this file if it can
MSGCFG.DAT It uses this file to determine whether or not a
message area is an echomail/netmail base. If it is,
the Color Code feature will be temporarily disabled.
DORINFO1.DEF - Drop file containing user information.
MSGHDR.ANS - Definable ANSI screen which, if found, will
replace the hardcoded screen header on the main
editing screen.
MSGINF. - File created by the BBS package containing message
MSG.INF information such as Source User, Target User,
message subject, & Message area.
MSGTMP. - File created by the BBS package containing Quoted
text.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Information ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
QuikEdit is a fullscreen ANSI message editor that was originally designed
for use with RemoteAccess. Although it has been tested with QuickBBS v2.xx
Telegard v3.00, RemoteAccess v2.xx, ProBoard v2.xx, Synchronet v2.xx,
TriBBS, AdeptXBBS v2.xx Watcom / v1.xx VAC and Concord v0.001 it should be
compatible with any other BBS that uses the QuickBBS style dropfiles that
contain the message writing information.
These files are MSGTMP & MSGINF. You should check your BBS documentation to
see if your software supports this system. QuikEdit also calls on the
Dorinfo1.Def file to read in necessary information about the user profile.
QuikEdit has a special feature specifically for QuickBBS, RemoteAccess, and
Telegard, which is Echobase checking. Do not enable this feature if you are
not using QuickBBS, RemoteAccess or Telegard.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ QuikEdit's System Requirements ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
QuikEdit requires the following to correctly operate on your system:
■ An IBM XT/AT/386/486/Pentium/P6+ or compatible
■ A modem, 300-115200 BPS
■ A FOSSIL communications driver (BNU/X00 or 100% compatible)
■ DOS 3.0+, OS/2 2.0+/Warp 3.0+/Warp 4.0+, Win 3.0+, DV 2.0+, or Win '95
■ DORINFO1.DEF (produced by your BBS program) (EXITINFO.BBS optional)
■ A terminal supporting ANSI emulation (user only)
■ 500k on your hard disk (plus space for dictionary & taglines)
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Configuration - Using EditCfg ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Setting up QuikEdit is quite easy. This section of the documentation will
attempt to take you step by step on how to use the configuration utility
EditCfg.Exe to set up QuikEdit. Most of the options are self explanatory.
You can use the local testmode feature at any time to test out how your
current settings will affect QuikEdit.Exe without having to save your
settings or exit the configuration program.
BEFORE YOU BEGIN: If you are using QuickBBS, RemoteAccess, or Telegard
it is recommended that you ensure that you've set your BBS package
environment variable so that you can take advantage of the added features
for these three BBS packages. The setup examples below will show you what
the environment variable is for the above BBS packages.
FILE
------
■ Save & Exit - This will save your current configuration to the
QuikEdit.Cfg file and will exit the program.
■ Save Without Exit - This will save your current configuration to the
QuikEdit.Cfg file and will allow you to continue modifying your setup.
■ Exit Without Save - This will abort the save procedure (just in case you
somehow really messed up!) and will exit the program.
■ System Paths -
■ Censor file - textfile containing censor keywords, one word per
line. If censoring is enabled, QuikEdit will read in the file and scan
the user's message for any matches of words within this file. If it
finds any matches, it will strike out that particular word from the
message. For example, if a censor word was "IDIOT", and the user
had a sentence such as:
"You are such an idiot!"
After the scan was complete the word "IDIOT" would be wiped out and
the result would be: "You are such an *****!".
A sample CENSOR.CFG file is included. The format is very simple; use
one word per line. QuikEdit is not case sensitive to the particular
censoring word that is being compared. Message censoring only takes
place AFTER the user opts to save their message. This is a registered
feature. {+}
■ Msg Header - a definable header which will be imported into the main
text body upon program execution.
■ Macros - path and filename to macro database.
■ Chat Util - path and filename to external chat utility. This can
be executed from within QuikEdit using the ALT-C key.
■ Dictionary - path and filename to words added to dictionary by
*sysop* -- this file must NOT be the same name as the
dictionary files --
■ Program Info - This will give you a little bit of information on the
current version of QuikEdit that you happen to be using.
■ Local Testmode - You can use this at anytime during configuration to
view how your current configuration will affect QuikEdit if you should
choose to save. You can execute a local testmode from the dos prompt
by running QuikEdit like this: QUIKEDIT.EXE /L
MANAGER
---------
■ Tagline Setup - This is a submenu containing all most of the tagline
setup. It can be accessed by unregistered users, however tagline
functions are limited.
TAGLINE SUBMENU
-----------------
■ Tagline Editor - Use this to edit all your compiled tagline files. You
can edit, insert, and import new taglines into your compiled files.
■ Compile Taglines - This file contains taglines that can be appended to
the ending of the users message if they opt to save their text.
This is a textfile that you can create, although a sample is included
called TagLines.Cfg. This file is encrypted, and MUST be compiled from
a textfile containing taglines. Use EditCfg to compile. At this time
there is not any considerable limitation on the number of taglines that
the file may contain. However, the more that there are, the longer it
will take EditCfg to read in the textfile and convert it to a
structured datafile.
IMPORTANT: The file extension of the compiled taglines file MUST be
a number. If you are using RemoteAccess with different message GROUPS,
it is possible to configure different tagline files for different
groups. If you are aren't using groups, or only want one tagline file,
it must be named in this format:
QUIKTAG.0
It must have the .0 extension to indicate one file. If you create a
file called QUIKTAG.2, if the message is being written in a conference
which falls in GROUP 2, then this tagline file will be accessed.
If QUIKNote can't find a corresponding tagline file, it will fall back
on QUIKTAG.0, so it would be a good idea to have a 'default' tagline
file.
■ Configure Toggles - This is another small submenu to toggle tagline
configuration. It consists of three options:
1) Use Taglines
2) List Taglines
3) Scroll Taglines
- If taglines aren't enabled, there will be no taglines.
- If only option (1) is enabled, a random tagline will be chosen for
the user.
- If options (1) and (2) are enabled, the user will be able to pick
from a random list of taglines.
- If all options are enabled, the user can browse the entire tagline
database.
■ Compile Dictionary - Use this to compile a textfile with a list of
words to a encrypted private dictionary file. This feature is used to
add words to the dictionary database that you wouldn't usually find in
an average English dictionary, Such as "QuickBBS", "FrontDoor" etc..
or any other slang terms that might be commonly used. Any words that
QuikEdit finds in this file will not be treated as mis-spelled. Note,
the textfile that contains the words MUST not be the same name as what
the compiled file will be called. Eg, if you have 'QUIKEDIT.PVT' as your
Private dictionary name, make sure you do not name the textfile with
this name before compilation.
■ Override Manager - Use this to define overrides for individual message
areas. You can toggle Pipe Codes, Taglines, Censoring, and ASNI
individually for every message base that your BBS has. This is for
QuickBBS, RemoteAccess and Telegard only. The settings defined will
override the default configuration settings.
■ Display Manager - This is a submenu containing toggles to turn certain
information fields ON or OFF on the main editing screen, as well as
configure screen locations.
Toggles
---------
■ View Macros YES/NO - Are users permitted to view the list of available
macros from within QuikEdit by using the CTRL-V key?
■ Create Macros YES/NO - Are users permitted to add to the list of
available macros from within QuikEdit by using the CTRL-V key?
NOTE: View Macros MUST be enabled for this feature to work.
■ Censor Tagline YES/NO - If the user uses inappropriate text in their
message and QuikEdit is forced to censor the text, should a tagline
be appended to the message to inform future message readers of that
fact? Eg. "*** This message has been censored by QuikEdit v2.40"
■ Imbedded Colors YES/NO - Should imbedded color codes be permitted? If
YES, when the message is saved, all color strings will be replaced by
ASNI escape sequences, thus putting colors into the message. Refer
below in "Editing Your Message In QuikEdit" for more information on
Color Strings.
■ Convert Colors YES/NO - Should QuikEdit convert color pipecodes to ANSI?
■ Use Overrides YES/NO - Should QuikEdit make use of the message override
definitions located in the MANAGER section?
■ Confirm Abort YES/NO - Should QuikEdit display a message to the user
if they choose to abort a message either by '/A', 'CTRL-A' or by use
of the help prompt which will ask them if they really want to abort their
message? Enabling this feature can help prevent accidental message
erasure.
■ Use Quote Color YES/NO - Should QuikEdit use the quote color selected in
EditCfg to make quoted text a specific color. If NO, all quoted text will
have regular text coloration.
■ Filter ASNI YES/NO - Should QuikEdit disrupt any ANSI that is read into
QuikEdit whether it be quoted text or manually imported text by the SysOP?
If NO, all ASNI codes will be treated normally.
■ Use Soft C/Rs YES/NO - Should QuikEdit use soft carriage returns in
messages, or should all lines be followed by a hard return?
■ KBT hangup YES/NO - Should QuikEdit terminate the connection when
the keyboard timeout has elapsed?
■ Speller Prompt YES/NO - Should QuikEdit prompt the user for spell checking
when they save their message?
■ CTRL-Q Quote Key YES/NO - Should QuikEdit open the quote window using
CTRL-Q? If not, it will use CTRL-W. On some systems using OS/2, the
operating system filters out the CTRL-Q before QuikEdit can intercept it
thereby making it impossible to quote from the main editing screen.
■ Suspend Time YES/NO - Should QuikEdit suspend user time while they are
editing their message?
■ Imbedded Files YES/NO - Should QuikEdit process imbedded file names. If
YES, QuikEdit will read in the external file that is specified and add it
to the message text. Eg: If the user put the following string on a line
by itself ..
%[MAIN.ANS]%
If QuikEdit can locate the file MAIN.ANS, it will import it into the
message text. Any files that you want to have imported MUST be surrounded
by the "%[" & "]%" brackets and should be placed on a single line without
any other text. You should specify the full path and filename of the file
to be imported. Please note, this function will PROPERLY import a file
into the message text, but editing before saving is not possible, as
all Imbedded files are processed when the user chooses to save.
■ Spell Checker YES/NO - Should users be permitted to make use of QuikEdit's
built in spell checking routines? If YES, users can access the spell
checker from the status bar. Please note, the spell checker does take a
little time, as it must cross reference every word with the dictionary.
Also, words smaller than 3 letters will not be checked.
■ Quote Ratio YES/NO - Should QuikEdit check to see if users have exceeded
the permitted percentage of quoted text?
■ Enforced Quote Ratio YES/NO - If the Quote Ratio is active, should
QuikEdit enforce it? If YES, QuikEdit will display a message telling
the user the current ratio, and that they must cut down. If NO,
QuikEdit will mention the ratios and display them, and ask the user if
they wish to re-edit the message before saving.
■ Upcase Ratio YES/NO - Should QuikEdit check to see if users have exceeded
the permitted percentage of Upcase text?
■ Enforce Upcase Ratio YES/NO - If the Upcase Ratio is active, should
QuikEdit enforce it? If YES, QuikEdit will display a message telling the
user the current ratio, and that they must cut down. If NO, QuikEdit will
mention the ratio and display it, and ask the user if they wish to
re-edit the message before saving.
■ Allow Linedraw YES/NO - Should users be allowed to enable linedraw mode?
■ Message Censor YES/NO - Should QuikEdit censor the message when the user
opts to save? This is a registered only feature. {+}
■ Quote Format YES/NO - Should QuikEdit reformat quoted text? Some editors
(such as DOS EDIT) when used in conjunction with BlueWave cause
messages to be afflicted with what is commonly known as the
"Chainsaw Effect", caused by Hard Returns. QuikEdit will now reformat
quoted text to remove this annoying problem.
■ QBBS compatible YES/NO - Is the BBS package you're running QuickBBS
compatible? (ie. QuickBBS, RemoteAccess, and Telegard as a few examples).
Does your BBS package support kludgelines? If you can answer YES to
either of these questions, turn compatibility ON!
■ Message Header YES/NO - Should QuikEdit import the sysop defined message
header upon execution?
■ Kludge filter YES/NO - If QuikEdit finds *defined* kludgelines in the
quoted text, should it filter them?
■ Errorlevels YES/NO - Should QuikEdit exit using the standard QBBS
compatible errorlevels?
■ Time Warning YES/NO - Should QuikEdit warn the user when less than 5
minutes remain?
Colors
--------
■ This section on color configuration is self explanatory. Simply select
the type of character which you wish to color configure. Another box
will appear that will show you the list of available colors. Type in
the number of the color you want to use.
■ DEFAULT SETTINGS will restore all the colors to their original
installation settings.
Macro Setup
-------------
■ Macro Editor - This will allow you to define replacement macros that
will be used within QuikEdit. For example, if you defined a macro such
as "QK" -> "QuickBBS", when the user types "QK" while editing their
message, QuikEdit will replace it with "QuickBBS". User Keywords are
not case sensitive, so if the user was to type "QK" or "Qk" Or "qK" or
"qk", each of these would still be replaced with "QuickBBS". This
function can be useful for correcting commonly misspelled words,
replacing shortforms, or "weeding out" inappropriate text (refer to
message censoring function as well). The macrofile used in QuikEdit is
completely compatible with QChat's macrofile, so you can interchange
the macro files between both pieces of software.
■ MacroFile Sorter - This will allow you to sort the macrofile in
alphabetical order by User Keyword. It will also strip the spaces
between macros to eliminate gaps.
■ Macro Triggers - Which characters (when typed after a macro) should
trigger the macro conversion? These characters usually consist of
punctuation.
Function Keys
---------------
■ This section is fairly simple. You can define different Function keys
(F1,F2..etc) to insert text into the message body while you are editing
your message. This is useful for greetings, goodbyes, and signatures
that are commonly used. For example, I might configure my Fn Keys like
this :
F1 - Take Care,
F2 - Later..
F3 - Benjamin
F4 - SysOP, Matrix Technologies
F5 - .. Author Of QuikEdit.
etc.. etc..
If I hit one of my Fn Keys while in QuikEdit, the appropriate text would
be inserted at the current cursor position. Function keys can also be
used to IMPORT files, such as multiline sigs. This is done by putting
the prefix '@' before the path to the file name. ie:
F1 - @SIG.TXT
If the file can't be found, it will simply do nothing. Make sure you
specify the full path for the file, or else QuikEdit will assume the
file should be in the current directory.
If you wish to run an external utility from within QuikEdit using the
function keys, simply use the '#' prefix in from the the commandline,
ie:
F1 - #D:\BBS\QUIKCHAT\QUIKCHAT.EXE -D:D:\BBS\RA
Assuming that the commandline is correct, the program will be executed.
Other
-------
■ Strike Symbol [*] - What character should QuikEdit use when striking out
text that can be found in the Censor.Cfg file. Asterisk ("*") is the
default.
■ SysOp Security - What is the SysOp security level to activate the
dictionary 'word-adding' feature.
■ Quote Ratio % - Up to what percentage is Quoted text allowed in the
message text.
■ Upcase Ratio % - Up to what percentage is upcase text allowed in the
message text.
■ # Of Taglines - What number of taglines should a user be allowed to pick
from when they have chosen to save their message? [1..10] (User makes
use of light bar to select tagline)
■ Dropfile Type - Which type of dropfile should QuikEdit use? (DORINFO1.DEF,
DORINFOX.DEF, or DOOR.SYS)
■ Kludge Codes - QuikEdit will filter kludges prefixed the the characters
configured in this section.
■ Menu Brackets - Configure left and right menu brackets surrounding
lightbar options, and some information fields.
■ Scroll Length - Configure total scroll length of main editing screen
when the end of page is reached.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With QuickBBS ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
QuickBBS Version 2.8x is supported FULLY in this version of QuikEdit, which
includes automatic integration of your existing BBS message areas, as well
as proper display of all message headers. QuikEdit and QuickBBS work
together offering your users a powerful option of a feature-laden full
screen editor package compared to others which barely supported QuickBBS
specific requirements in years past.
The following documentation will help you, a QuickBBS SysOp, to
successfully integrate QuikEdit into your system, seamlessly...
INSTALLING QUIKEDIT VIA QCONFIG (FULL SCREEN EDITOR SETTINGS):
-------------------------------------------------------------
Go into QCONFIG, and pull down these menus: Messages -> External Editor
Install accordingly, adjusting paths as necessary (example below):
╒═════════════════════External Message Editor Setup══════════════════════╕
│ │
│ Message Reply Quoting String: @> Swap to Disk/EMS: Yes │
│ │
│ DOS Command String: │
│ C:\QuickBBS\QuikEdit\QuikEdit.Exe /N:*N │
│ │
╘════════════════════════════════════════════════════════════════════════╛
(The above example assumes "C:\QuickBBS\QuikEdit\" is the path containing
the QuikEdit distribution files, please adjust accordingly for your
platform.)
Note for calling QuikEdit as a DOOR from a menu:
If you load QuikEdit as a door, via a TYPE 7 command in a menu, issue the
following command on the "optional data" line (example):
*C /C *M C:\QuickBBS\QuikEdit\Quikedit.exe /N:*N
(Make sure the swap, *M, is there, and pass the node# to QuikEdit as shown)
CONFIGURATION INFORMATION: EDITCFG.EXE
======================================
New Users to QuikEdit who run QuickBBS, please note:
*Before* running EDITCFG.EXE, make sure your "QUICK" environment variable
is set properly in your batch file(s) used to load the BBS, or autoexec.bat.
This environment variable should already be enabled, according to the
QuickBBS documentation. This variable, such as "SET QUICK=C:\QuickBBS",
points to your main BBS path, where MSGCFG.DAT lives along with other BBS
data files. EDITCFG.EXE looks for this environment variable the first time
it is run, and if found it automatically configures sensible defaults, and
enables the following integrated features:
* QuikEdit reads in your message areas directly, automatically!
* QuikEdit creates certain toggles and defaults which work well with
QuickBBS!
So make sure the "QUICK" environment variable is set, and active, when
you run EDITCFG.EXE for the first time if it's not already.
IMPORTANT CONFIGURATION CONCERNS WITHIN EDITCFG.EXE
---------------------------------------------------
Did you know all your QuickBBS defined message areas are loaded by
EDITCFG.EXE, and set to sensible defaults, automatically? Also,
various sensible QuickBBS toggles and features are set:
* By reading in your message areas, via EDITCFG.EXE, the following defaults
are given to the message areas on your BBS, automatically (and can be
easily overridden via "Area Manager" settings):
* Private areas will have censorship options DISABLED
* Networked ECHO areas will have PIPECODES and ANSI disabled
* Kludge code of CONTROL-A (ASCII 1) is used
* Proper errorlevels are issued for aborted messages under QuickBBS
* SysOp security level and associated options should be set to 32000 or
whatever YOUR access level is on your system if you need to override.
* DORINFO1.DEF, DOOR.SYS are both supported and either can be enabled
under version 2.8x of QuickBBS. Version 2.76a users, must use
DORINFO1.DEF.
* Since QuickBBS does not utilize "message number" fields in version 2.8x,
you can easily toggle this setting via "Display Manager" settings menu
as well as the other header fields (both location and availability) if
desired, but are set to work with QuickBBS's MSGTMP and MSG.INF files,
automatically.
* Under "Toggle 2", make sure "QBBS Compatible" is set to YES, which should
be set as the default if the "QUICK" environment variable is set
properly and active prior to the first time EDITCFG.EXE is run.
* REMOTE file import mode for SysOps, initiated by CONTROL-F when entering a
message, is now supported as requested by QuickBBS users.
* LOCAL file import, ALT-F2, is supported also!
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With RemoteAccess ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into RA. Failure to
setup QuikEdit correctly before installing it into your bbs program will
probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU should work fine with QuikEdit.
If you don't have a fossil driver installed, a simple error message will
be displayed, and the program will stop. A fossil is NOT required when
running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your RemoteAccess setup.
1. Extract all the files in the distribution archive to a directory of your
choice. C:\RA\QuikEdit is recommended and is assumed to be the directory
you are using from now on. If you haven't set the RA Environment Variable
in your AUTOEXEC.BAT yet, make sure you do before proceeding to the next
step.
Eg. SET RA=C:\RA
It is further suggested that you set the QuikEdit Environment Variable
to insure QuikEdit will always find it's file.
Eg. SET QuikEdit=C:\RA\QuikEdit
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up
QuikEdit.
3. If you had the RA Environment Variable set in your AUTOEXEC.BAT prior
to configuring QuikEdit, EditCfg.Exe should have automatically setup
QuikEdit into RA.
If you didn't have the RA Environment Variable set QuikEdit needs to be
setup in RACONFIG.EXE so that when the user attempts to write a message
it calls up QuikEdit and NOT the internal RemoteAccess line-by-line
editor. Change to your RemoteAccess directory and run RACONFIG.EXE. Go
to Options -> Messages -> External Editor. Place the command-line to
run QuikEdit.Exe in this space. Eg.
╒════════════════════════════════ External editor command-line ╕
│ │
│ C:\RA\QUIKEDIT\QUIKEDIT.EXE -N:*N *M░░░░░░░░░░░░░░░░░░░░░░░░ │
│ │
╘══════════════════════════════════════════════════════════════╛
If you wish, you can specify the path to the dropfiles read in by
QuikEdit (Dorinfo1.Def, MsgInf, and MsgTmp if it exists) by adding
the following parameter to your commandline like this:
╒════════════════════════════════ External editor command-line ╕
│ │
│ C:\RA\QUIKEDIT\QUIKEDIT.EXE /D:C:\RA -N:*N *M░░░░░░░░░░░░░░░ │
│ │
╘══════════════════════════════════════════════════════════════╛
Otherwise QuikEdit will assume the dropfiles are located in the current
directory (usually your BBS directory)
If you are PLANNING TO RUN QUIKEDIT FROM YOUR NEWUSER.Q-A, then you
should use the following commandline in your RaConfig setup.
C:\RA\QUIKEDIT.EXE /B:*B /P:*P /T:*T *M
*B - Passes the baudrate out to the commandline.
*P - Passes the modem port out to the commandline.
*N - Passes the nodenumber as read from the %TASK% environment variable
out to the commandline.
*M - Activate the MemorySwap feature.
*T - Passes time limit out to the commandline.
4. When you run QuikEdit, be sure that the QuikEdit.Cfg file has been created.
If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt
to run QuikEdit.Exe directly, QuikEdit will display an error message that
QuikEdit.Cfg doesn't exist.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With ProBoard ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into PB. Failure to
setup QuikEdit correctly before installing it into your bbs program will
probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your PB setup.
1. Extract all the files in the distribution archive to a directory of your
choice. C:\PB\QuikEdit is recommended and is assumed to be the directory
you are using from now on.
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up QuikEdit.
3. QuikEdit needs to be setup in PROCFG.EXE so that when the user
attempts to write a message it calls up QuikEdit and NOT the
internal ProBoard line-by-line editor. Change to your ProBoard
directory and run PROCFG.EXE. Go to Options -> Paths -> Editor Cmd and
place the command-line to run QuikEdit.Exe in this space like the
example below:
╔════════════════════ Paths ═══════════════════╗
║ ║
║ Textfiles : C:\PB\TXTFILES\ ║
║ RIP files : C:\PB\RIP\SCRIPTS\ ║
║ RIP icons : C:\PB\RIP\ICONS\ ║
║ Menus : C:\PB\MENUS\ ║
║ Messagebase : C:\PB\MSGBASE\ ║
║ Uploads : C:\PB\FILES\UPLOADS\ ║
║ Pvt Uploads : C:\PB\PVTFILES\ ║
║ Nodelist Dir: C:\PB\NODELIST\ ║
║ PEX files : C:\PB\PEX\ ║
║ ║
║ Editor Cmd : *C /C C:\PB\QUIKEDIT\QUIKEDIT.EXE /D:X:\PB\
║ Use internal fullscreen editor? No ║
║ ║
║ Extern.Chat : ║
║ ║
╚══════════════════════════════════════════════╝
If you are running a Multi-Node bbs, you must specify the path to the
dropfiles read in by QuikEdit (Dorinfo1.Def, MsgInf, and MsgTmp if it
exists) by adding the following parameter to your commandline like
this:
Editor Cmd : *C /C X:\PB\QUIKEDIT\QUIKEDIT.EXE /D:X:\PB\NODE*# /N:*#
Otherwise QuikEdit will assume the dropfiles are located in the current
directory (usually your BBS directory)
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With Telegard ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into TG. Failure to
setup QuikEdit correctly before installing it into your bbs program will
probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your Telegard setup.
1. Extract all the files in the distribution archive to a directory of
your choice. C:\TG\QuikEDIT\ is recommended and is assumed to be the
directory you are using from now on. Be sure to set the Telegard
Environment Variable if you haven't already.
Eg. SET TG=C:\TG
QuikEdit will read this Environment Variable and Auto Configure itself
into Telegard once you run EditCfg.Exe, if it is not set you will have
to manually setup QuikEdit in Telegard.
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up QuikEdit.
3. QuikEdit needs to be setup in Telegard so that when the user has a
choice to either use the internal line-by-line editor or using
QuikEdit. If you had the Telegard Environment variable set when you
ran Editcfg it should have automatically setup QuikEdit in Telegard.
If you did not have the Environment Variable set you can accomplish this
by doing the following. Go to your Telegard directory, run Telegard.EXE.
Go to "S"ystem Config -> "M"essage System -> "P" Full Screen Editor.
Place the command-line to run QuikEdit.Exe in this space.
Message System Configuration
A. Define system addresses
B. Default area configuration
C. User access configuration
D. Netmail status Kill J. Upload messages Enabled
E. Hold all netmail Yes K. Userlist lookup Disabled
F. UUCP email gate Disabled L. Nodelist lookup Disabled
G. Antiquated UUCP No M. SmartQuote Enabled
H. Honour RRQ Yes N. QuickQuote Disabled
I. Space to post 100K O. Confirm FSE Save Enabled
P. FSE command "C:\TG\QUIKEDIT\QUIKEDIT.EXE"
R. FSE non-abort Internal
S. FSE doortype RBBS-PC (DORINFO1.DEF)
T. Nodelist Invalid, ""
U. Write logging Disabled
Enter selection or (Q)uit :
4. When you run QuikEdit, be sure that the QuikEdit.Cfg file has been
created. If it has not, then you MUST run EditCfg.Exe. If you don't,
and attempt to run QuikEdit.Exe directly, QuikEdit will display an error
message that QuikEDIT.CFG doesn't exist.
5. Be sure to set the QuikEDIT environment variable for this above setup,
if it is left out, you will receive errors.
Eg. SET QUIKEDIT=C:\TG\QuikEdit
There are many different ways of setting up QuikEdit to work with Telegard.
This above way is one way it will work, if you know another way that works
then by all means, use it. This is meant for the first time beginner who
does not know how to setup QuikEdit with Telegard.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With SynchroNet ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into Synchronet.
Failure to setup QuikEdit correctly before installing it into your bbs
program will probably result in QuikEdit failing to run or not running as
expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your Synchronet setup.
1. Extract all the files in the distribution archive to a directory of
your choice. C:\SBBS\QuikEdit is recommended and is assumed to be the
directory you are using from now on.
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up QuikEdit.
3. QuikEdit needs to be setup in Synchronet so that when the user
attempts to write a message it calls up QuikEdit and NOT the
internal Synchronet line-by-line editor. Change to your Synchronet
Node directory and run SCFG.BAT or SCFG.CMD. Go to External Programs ->
External Editors. Hit Insert and enter the name for the External Editor
Eg. QuikEdit, you can leave the External Editor Internal code QuikEdit
ot change it to what you want. Now you will be back to the External
editors screen, highlight QuikEdit and hit enter. Now you can configure
QuikEdit to be used with Synchronet as shown below:
╔═════════════════════╗░░░░╔═══════════════════════════════════════════╗
║ External Programs ║░░░░║ External Editors ║
╠═════════════════════╣░░░░╠═══════════════════════════════════════════╣
║ │Fixed Events ║░░░░║ │SYNCEDIT %!syncedit %! %l %f ║
║ │Timed Events ║░░░░║ │QUIKEDIT \sbbs\quikedit\quikedit /D:X:║
║ │Global Swap List ║░░░░║ │ ║
║ │OS/2 Program List ║░░░░╚═══════════════════════════════════════════╝
║╔════════════════════════════════════════════════════════════════════╗
║║ QuikEdit Editor ║
╚╠════════════════════════════════════════════════════════════════════╣
║ │Name QuikEdit ║
║ │Internal Code QUIKEDIT ║
║ │Local Command Line \sbbs\quikedit\quikedit /D:X:\SBBS\NODE%# /N:%#
║ │Remote Command Line \sbbs\quikedit\quikedit /D:X:\SBBS\NODE%# /N:%#
║ │Access Requirements ║
║ │Intercept I/O Interrupts No ║
║ │Quoted Text Prompt User ║
║ │QuickBBS Style (MSGTMP) Yes ║
║ │Expand Line Feeds to CRLF Yes ║
║ │BBS Drop File Type RBBS/QuickBBS DORINFO1.DEF ║
╚════════════════════════════════════════════════════════════════════╝
4. When you run QuikEdit, be sure that the QuikEdit.Cfg file has been created.
If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt
to run QuikEdit.Exe directly, QuikEdit will display an error message that
QuikEdit.Cfg doesn't exist.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With AdeptXBBS ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into Adept. Failure to
setup QuikEdit correctly before installing it into your bbs program will
probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your AdeptXBBS setup.
1. Extract all the files in the distribution archive to a directory of your
choice. C:\Adept\QuikEdit is recommended and is assumed to be the
directory you are using from now on. Set the QuikEdit Environment Variable
in your AUTOEXEC.BAT:
Eg. SET QuikEdit=C:\Adept\QuikEdit
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up
QuikEdit.
3. AdeptXBBS doesn't have an area to configure an External Fullscreen Editor,
instead it uses a REXX script to call it up. Enclosed in the QuikEdit
archive you should find a file called Adept.Zip which contains extfse1.cmd
and QuikEdit.bat.
Unzip the archive in your AdeptXBBS main directory using the -d option
to extract sub-directories and the file will be placed in the proper
directories. If somethin goes wrong, make sure extfse1.cmd is in your
Adept Menus directory and QuikEdit.Bat in in you Adept Main Directory.
Be sure to edit the extfse1.cmd file to reflect the drive and directory
that you have your Adept setup in as well as editing the QuikEdit.Bat to
reflect the drive and directory where you installed QuikEdit.
Once these files are in place, Adept will call up QuikEdit automatically
instead of using the internal fullscreen editor. If you want to run
QuikEdit while on locally, copy extfse1.cmd to extfse0.cmd, the same goes
if you run a Multi-Node system, copy extfse1.cmd changing the 1 to the
node number you want it to be called from.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With Concord ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into Concord. Failure
to setup QuikEdit correctly before installing it into your bbs program
will probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your Concord setup.
1. Extract all the files in the distribution archive to a directory of your
choice. C:\CONCORD\QuikEdit is recommended and is assumed to be the
directory you are using from now on. Set the QuikEdit Environment Variable
in your AUTOEXEC.BAT:
Eg. SET QuikEdit=C:\Concord\QuikEdit
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up QuikEdit.
3. QuikEdit needs to be setup in CSETUP.EXE so that when the user
attempts to write a message it calls up QuikEdit and NOT the
internal Concord full screen editor. Change to your Concord directory
and run CSETUP.EXE. Go to General -> FS Message Editors -> Fullscreen
Edit and place the command-line to run QuikEdit.Exe in this space like
the example below:
┌─────────────────────────────────────────────────────────────────────────┐
│ │
│ Active? : Yes │
│ Description : Fullscreen edit │
│ Selection key: E │
│ Command line : *C /C X:\CONCORD\QUIKEDIT\QUIKEDIT.EXE /D:X:\CONCORD *N │
│ │
└─────────────────────────────────────────────────────────────────────────┘
4. When you run QuikEdit, be sure that the QuikEdit.Cfg file has been created.
If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt
to run QuikEdit.Exe directly, QuikEdit will display an error message that
QuikEdit.Cfg doesn't exist.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Setting Up QuikEdit.Exe With TriBBS ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Please read the section of this document entitled 'Program Information -
Using EditCfg' BEFORE attempting to install QuikEdit into TriBBS. Failure
to setup QuikEdit correctly before installing it into your bbs program will
probably result in QuikEdit failing to run or not running as expected.
In order to run QuikEdit.Exe with a user ONLINE, you must have a fossil
driver active. A fossil driver such as BNU or X00 should work fine with
QuikEdit. If you don't have a fossil driver installed, a simple error
message will be displayed, and the program will stop. A fossil is NOT
required when running locally.
**Note** : Do _NOT_ write protect _ANY_ Of the QuikEdit files, if you do,
QuikEdit will ignore them, and therefore not run properly.
We will now run through EVERYTHING you need to do in order to get QuikEdit
to run in your TriBBS setup.
1. Extract all the files in the distribution archive to a directory of your
choice. C:\TriBBS\QuikEdit is recommended and is assumed to be the
directory you are using from now on. Set the QuikEdit Environment Variable
in your AUTOEXEC.BAT:
Eg. SET QuikEdit=C:\TriBBS\QuikEdit
2. Run EditCfg.Exe and configure all of QuikEdit's options as explained
earlier in this document. You MUST configure QuikEdit for it to work
correctly! Refer to the section of this document for setting up
QuikEdit.
3. In TriBBS, whenever the caller uses the full screen editor, TriBBS will
check for an EDITOR.BAT file in the TriBBS directory. If found, TriBBS
will run the batch file instead of using it's internal full screen
editor. Because TriBBS swaps itself out of memory to run EDITOR.BAT,
you shouldn't call BOARD.BAT at the end of EDITOR.BAT to rerun BBS.EXE.
Create a file Called Editor.Bat like the Example below in your TriBBS
directory:
echo off
cd\TriBBS\QuikEdit
QuikEdit /n:1 /D:C:\TriBBS
If you are running a Multi-Node TriBBS System, you will need to make a
Editor.Bat for each node like the Examples below:
[Editor.Bat for Node 2]
echo off
cd\TriBBS\QuikEdit
QuikEdit /n:2 /D:C:\TriBBS2
[Editor.Bat for Node 3]
echo off
cd\TriBBS\QuikEdit
QuikEdit /n:1 /D:C:\TriBBS3
4. When you run QuikEdit, be sure that the QuikEdit.Cfg file has been created.
If it has not, then you MUST run EditCfg.Exe. If you don't, and attempt
to run QuikEdit.Exe directly, QuikEdit will display an error message that
QuikEdit.Cfg doesn't exist.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Errorlevels Generated By QuikEdit ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Once QuikEdit's execution has ended, it will generate one of two errorlevels
under normal termination.
0 - If QuikEdit terminates with errorlevel 0, it means that the message
has been successfully saved, and should be processed by the BBS
package.
1 - If QuikEdit terminates with errorlevel 1, it means that the message
has either been aborted; or, that the user attempted to save a blank
message. In either case, the BBS package should treat the message as
aborted, and NOT process the message.
2 - If QuikEdit terminates with errorlevel 2, it means that the user's
keyboard has been inactive for more than the maximum time allowed.
The program has terminated, and may have saved the message body to
the MSGTMP file (or equivalent) if autosaving is enabled.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Files That Are Used By QuikEdit ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
QuikEdit will call upon a number of files during runtime. They are listed
below along with a brief description.
CENSOR.CFG - This is a textfile containing inappropriate words that
QuikEdit will strike out of the message text when they are
encountered. {+}
CONFIG.RA - This file is read ONCE only by EDITCFG when you first
CONFIG.TG install QuikEdit. It will only be read if EditCfg can find
QUICKCFG.DAT the BBS environment variable. It is compatible with the
QuickBBS v2.8x, RemoteAccess v2.xx and Telegard v3.0x
configuration files only. It will not read the Ra 1.1x
format.
COL_HELP.ANS - This is an ASNI file that will be displayed that will
replace the hardcoded color help menu. You can create
this with an ANSI editor such as TheDraw.
DORINFO1.DEF - This is the dropfile that most BBS packages can create
that holds important user profile information.
EDITHDR.TXT - This file will be imported into the beginning of the
message if it is enabled, and QuikEdit can locate it. It
should be in the main QuikEdit directory.
QUIKEDIT.CFG - This is QuikEdit's configuration file. It is absolutely
necessary in order for QuikEdit.Exe to function.
QUIKEDIT.DIC - This is the QuikEdit dictionary that is used in conjunction
with the spellcheck feature. It comes in a separate package
from the main QuikEdit program, due to its size.
QUIKEDIT.IDX - This is the QuikEdit dictionary index file that comes with
the dictionary. It is also located in the secondary package.
QUIKEDIT.MDX - This file is scanned by QuikEdit if you are using RA, and
have run EDITCFG.EXE INDEX. This file is an index that
contains the current toggle settings for all message areas.
Toggle settings include taglines, pipecodes, ASNI
filtering, and message censoring.
KEY_HELP.ANS - This is an ASNI file that will be displayed that will
replace the hardcoded Userkey help menu. You can create
this with an ASNI editor such as TheDraw.
MACRO.CFG - This is the file that contains the replacement macros that
can be used in QuikEdit. It is compatible with the MACRO.CFG
file that QuikChat uses. This file must be edited using
EDITCFG.EXE.
MSGHDR.ANS - An ANSI screen which QuikEdit will use instead of the
default screen header on the message editing screen.
MSGINF. - This file contains message writing information.
MSG.INF
MSGTMP. - This file can contain both quoted message text as well as
the regular message text that will be read back in by the
BBS package.
QUIKTAG.### - This is a tagline database that QuikEdit will use to pick
a random tagline to be appended to the end of messages. {+}
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ QuikEdit.Exe Commandline Parameters ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Note: ALL Commandline parameters are optional, and do NOT have to be used
unless you are trying something new and different with QuikEdit =). Generally
these parameters are only used with you are trying to run QuikEdit without
a DORINFO1.DEF file (such as an offline mail reader)
/B:[BAUD] - Use this parameter to specify the baudrate.
Eg. QUIKEDIT.EXE /B:14400
/BW - Use this parameter to tell QuikEdit that you are using an
offline mail reader, such as BlueWave. If this is the
case, your commandline generally will not use any of the
other commandline parameters.
/D:[PATH] - Use this parameter to specify the path ONLY to the
dropfiles that are to be used by QuikEdit (DORINFO1.DEF,
MSGTMP, MSGINF) Eg. QUIKEDIT.EXE /D:C:\QuickBBS\Node2
/F:[FILENAME] - Use this parameter to change the default textfile name
that message text will be stored in. (Default = "MSGTMP")
This is useful for offline mail readers.
Eg. QUIKEDIT.EXE /F:MSGTEMP.BBS
/FORCE - Use this parameter to make sure that the user can't
abort the message they are writing. This is useful for
NewUser Questionnaires, where you want to make sure the
user actually writes an introductory comment.
/K:[TIMEOUT] - Use this parameter to specify in SECONDS how long QuikEdit
will wait in keyboard inactivity before disconnecting.
/L - Use this parameter to run QuikEdit in local test mode.
Eg. QUIKEDIT.EXE /L
/N:[NODE] - Use this parameter to specify the NODE that QuikEdit is
being run on. A MUST FOR MULTINODE SYSTEMS!!!!!!
(Default = 1)
/P:[COMPORT] - Use this parameter to specify comport to be used by
QuikEdit. If you port is com3, then this is the
commandline: QUIKEDIT.EXE /P:3
/T:[MINUTES] - Use this parameter to specify the amount of time
remaining for the user. Eg. QUIKEDIT.EXE /T:30
Please note: If you change any values above that correspond with values
in the DORINFO1.DEF File, then the DORINFO1.DEF value will
be ignored.
There is one more parameter that was added in during the v1.60 betas.
I had planned on removing it, however I've left it in for those who
really need to fine-tune QuikEdit to their system. This parameter controls
how much timeslicing will occur in multitasking environments. The LARGER
the value, the LESS slicing that occurs. QuikEdit defaults to 20, which
was the optimum value on all test systems. Following is a symptom/solution
chart:
Symptom: | Solution:
-------------------------------------------------------------------------
QuikEdit, when run in a | QuikEdit is giving up TOO many timeslices
multitasking environment is | in your multitasking environment. You
really slow, although the | should INCREASE the value, so that QuikEdit
other windows run fine. | gives LESS timeslices.
-------------------------------------------------------------------------
QuikEdit runs absolutely | QuikEdit is "hogging the CPU" (it's not
great in my environment, | giving up enough timeslices). Correct for
with no lag or delays. | this by DECREASING the value, so that
However, while QuikEdit is | QuikEdit gives up time slices more
running, my other windows | frequently.
slow to a crawl. |
-------------------------------------------------------------------------
The parameter to use to adjust QuikEdit's slicing is:
/S:[value] - [value] represents the slice value, as outlined above.
We recommend you play with this only if *** YOU REALLY
KNOW WHAT YOU'RE DOING! ***
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Editing your message in QuikEdit ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Function Keys
---------------
To make message editing go easier, there are a number of different keys that
may be used by both the SysOP and the user. A list follows:
UP ARROW - Moves the cursor up one line
DOWN ARROW - Moves the cursor down one line
LEFT ARROW - Moves the cursor to the left one space
RIGHT ARROW - Moves the cursor to the right one space
INSERT - Toggle the text insert/typeover mode
DELETE - Delete the character currently under the cursor
CTRL-A or /A - Abort message text & exit program
CTRL-B - Restore line of text from buffer
CTRL-C - Center the current line of text on the screen
CTRL-D - Move cursor to the right one space
CTRL-E - Move cursor up one line
CTRL-F - Remotely import a file (SYSOP ONLY)
CTRL-J - Left justify the current line of text on the screen
CTRL-K - Toggle LineDraw mode ON or OFF, or select line style
CTRL-L - List / edit available macros
CTRL-P - Place cursor at the end of the line
CTRL-Q or /Q - Quote window (Available only with message replies)
CTRL-R - Redraw the editing screen
CTRL-S - Move cursor to the left one space
CTRL-T - Delete text from the cursor to the end of the line
CTRL-U - Delete text from the cursor to the end of the current word
CTRL-V - Toggle INSERT/TYPEOVER Modes
CTRL-W or /Q - Quote window (Available only with message replies)
CTRL-X - Move cursor down one line
CTRL-Y - Erase current line of text
CTRL-Z or /S - Save message text & exit program
There are also SysOP only keys that may be used:
F1.. 10 - Activate previously defined SysOp text macros
ALT- F2 - Import a textfile into the message
ALT- F3 - Export message contents to a file
ALT- C - Invoke external chat utility
ALT- H - Terminate Connection
ALT- J - Shell to DOS
ALT- = - Add one minute to user's time
ALT- - - Subtract one minute from user's time
Imbedded Replacement Strings
------------------------------
All replacement macros, taglines and SysOp function keys can make use of
the following built in control strings (NOTE ** Some are repeated to ensure
compatibility with QUIKCHAT replacement strings) :
@A = SysOp name (Read From QuikEdit Configuration)
@B = BBS name (Read From QuikEdit Configuration)
@C = Receiving users full name
@D = Date
@H = Message subject
@F = Receiving users first name
@R = Receiving users first name
@S = SysOp name (Read From QuikEdit Configuration)
@T = Time of day
@U = Sending user's first name
@V = Program version number
The control strings can be used in the following manner. For Example, if
you were configuring one of your macros to tell the current time & Date,
you could put:
"MTD" -> "This message was written at @T on @D."
And then when QuikEdit is run, if the user chooses to type in the "MTD"
macro, the strings would be replaced and the result would be:
"This message was written at 2:41p on 07/31/97."
All the control strings can be used in a similar manner in all the other
macros & taglines, and Fn keys.
Imbedded Colors
-----------------
With QuikEdit, it is possible to use color codes into your Message text.
This is very easily done. Wherever you would like to have a color change in
your message, use one of the following color combinations:
0 - Black 8 - DarkGray
1 - Blue 9 - LightBlue
2 - Green A - LightGreen
3 - Cyan B - LightCyan
4 - Red C - LightRed
5 - Magenta D - LightMagenta
6 - Brown E - Yellow
7 - LightGray F - White
Combine these color codes to create a foreground & background color.
ie. |4E would yield yellow foreground on red background
The first value represents the background color, the second value
represents the foreground color.
So, If you had a line such as:
"|15This is a |09test."
The first three words "This is a" would be in White, and the rest, "Test."
would be in LightBlue once the message has been saved.
Please be aware of two important points. Firstly, QuikEdit will NOT CHANGE
the color WHILE YOU ARE EDITING the message. Color strings will be
converted when the message is saved. Second, these codes are replaced with
ASNI escape sequences (the same codes that are used in your ASNI screens).
Many networks do not authorize ASNI escape codes in their echos. If you
are going to make use of this feature, it is recommended that users are
informed on the point that they should not use embedded color strings in
echomail areas. If you are using RemoteAccess, it is possible to make
QuikEdit determine whether or not the message area is a local base. If it is
NOT, QuikEdit can automatically temporarily disable Imbedded colors in the
message that the user is writing.
Imbedded Files
----------------
With QuikEdit, it is possible to have external filenames that will be later
imported into into your Message text. This is very easily done. Wherever
you would like to have a file imported into your message, use the following
method. For Example, say you have a textfile with some type of header in it
that you want to import into your message. The filename of the header is
BBSHDR.ASC for our example. In your message you would put the following on
a blank line of text:
%[BBSHDR.ASC]%
When your message is saved, QuikEdit will seek out the filename between the
two special brackets ( %[ and ]% ). You can specify the path of the file
as well, if the file is not located in your current directory, for example:
%[C:\BBS\TXTFILES\BBSHDR.ASC]%
When the message is saved, QuikEdit will find this file, and import it into
the body of the message text, so your message might end up looking like
this:
┌──────┐┌──┐┌──┐┌───┐┌──┐ ┌──┐┌─────┐┌───────┐┌───┐┌───────┐
│░▒┌┐░▒││░▒││░▒││░▒▓││░▒│┌┘░┌┘│░▒▓┌─┘│░▒▓┌┐░▒││░▒▓│└─┐░▒▓┌─┘
│▒▓││▒▓││▒▓││▒▓││▒▓█││▒▓└┘ └─┐│▒▓█└┐ │▒▓█││▒▓││▒▓█│ │▒▓█│
│▓█││▓█││▓█││▓█││▓██││▓█┌──┐▒││▓██┌┘ │▓██││▓█││▓██│ │▓██│
│██└┘██││██└┘██││███││██│ │▓││███└─┐│███└┘██││███│ │███│
└──────\└──────┘└───┘└──┘ └─┘└─────┘└───────┘└───┘ └───┘
Please be aware of an important point. QuikEdit will NOT IMPORT the file(s)
WHILE YOU ARE EDITING the message. File(s) will only be imported when the
message is saved.
LineDraw Mode
---------------
QuikEdit has a "linedraw" mode. When the user activates this mode, it is
possible to draw High-Bit ASCII lines on the screen by using the Cursor
Keys (Left, Right, Up, Down). There are 3 line styles available:
1) ╔═╗
2) ╒═╕
3) ┌─┐
And that's all there is to it.. Hope you guys enjoy this thing, and it is
my hope that QuikEdit becomes the default editor used with your system =-)
┌────────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Other Matrix Technologies Utilities ▓▓▓▒▒▒░░░│
└────────────────────────────────────────────────────────────────────────────┘
Here is a list of all the Matrix Technologies utilities that were available at
the time of release of this archive. If you enjoy using this utility,
you may want to check some of these out! :)
■ QChat -
QChat is a split screen chat utility for QuickBBS, RemoteAccess,
ProBoard, AdeptXBBS, Telegard, and SynchroNet BBS packages. It can be
used with many other BBS types as long as they support Dorinfo1.Def
or Door.Sys type Doors.
■ QuikEdit -
QuikEdit is a fullscreen ANSI message editor that was originally designed
for use with RemoteAccess. Although it has been tested with RA v2.xx,
QuickBBS v2.xx, ProBoard v2.xx, Telegard v3.0, AdeptXBBS, and SynchroNet
it should be compatible with any other BBS that uses the QuickBBS style
dropfiles that contain the message writing information.
These files are MSGTMP & MSGINF. You should check your BBS documentation
to see if your software supports this system. QuikEdit also calls on the
Dorinfo1.Def file to read in necessary information about the user profile.
■ QuikBank -
QuikBank is a fully functional, fully configurable timebank system
for QuickBBS v2.xx, RemoteAccess v2.xx and ProBoard v2.xx. It has many
cool features, including InterBBS transactions.
■ QuikCBV -
QuikCBV is a Full featured callback verification system for RemoteAccess
and ProBoard. Many unique features! Look forward to even more features
in the next version!
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Support - Internet Email Addresses ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
Following is a list of support/distribution/registration sites which
currently have Internet email addresses. Please contact any of the sites
listed in SUPPORT.DOC via email for assistance with any Matrix Technologies
product.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ Program Support - BBS Locations ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
All Matrix Technologies utilities are available from our homepage at:
http://www.isonline.com/Matrix
QuikEdit can be File Requested from any of the BBS's listed in
SUPPORT.DOC, which is included in this archive.
┌───────────────────────────────────────────────────────────────────────────┐
│░░░▒▒▒▓▓▓ End Of QuikEdit Documentation ▓▓▓▒▒▒░░░│
└───────────────────────────────────────────────────────────────────────────┘
